An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hi everyone, I'm an indie developer in Taiwan and also a Zi Wei Dou Shu and BaZi consultant. I built this app for my own work and for other practitioners. The app focuses on client case management: client records, consultations and payments in one place, filtering across cases (by chart features, life events or payment status), and statistics to review the business and explore how traditional rules relate to their own cases. It also generates charts, which users interpret themselves, and on iPad two pages can be viewed side by side. It has been rejected several times under Guideline 4.3(b), with the message that it "primarily features astrology, horoscopes, palm reading, fortune telling or zodiac reports." It has no horoscopes, palm reading, daily fortunes, zodiac reports or AI readings. I've provided review notes and a demo video to explain its features. The latest rejection noted that repeated submissions may lead to extended review times, and that accounts that repeatedly submit non-compliant apps may be removed from the Apple Developer Program. So I'd like to better understand the concerns before submitting again. It also suggested a web app. Our web version is already live and used by many paying users, but I find the native version smoother to use on iPhone and iPad. I respect the review process, but this has been discouraging. I'm planning to request an App Review appointment and am considering an appeal to the App Review Board. I'd love to hear from others: Has anyone with a professional tool in a crowded category been approved after a 4.3(b) rejection? What made the difference? If you've met with App Review or appealed to the Board, what information helped them understand your app? Thanks for reading. Any advice would mean a lot.

Hi everyone, I'm a new iOS developer, and my first app has been rejected twice because of In-App Purchase issues. Setup: Flutter, in_app_purchase 3.3.0, in_app_purchase_storekit 0.4.10 (StoreKit 1) One auto-renewable subscription and one non-consumable lifetime purchase Both products show "Ready for Review" in App Store Connect. Paid Apps Agreement is active. First review: The prices were visible on an iPad, but the subscription purchase failed (Guideline 2.1(b)). Second review: Neither product showed a price on an iPhone (Guideline 2.1(b)). Apple also noted missing subscription information (Guideline 3.1.2(c)). On my iPhone 15, both products load correctly and test purchases work in TestFlight using my regular Apple Account. Product IDs, pricing, availability, and localizations appear correct. My question: What could cause queryProductDetails / SKProductsRequest to return no products during App Review when everything works in TestFlight? Any suggestions would be greatly appreciated. Thanks! :)

Ok, I’m an individual Apple developer. On September 5, 2026, I submitted export-compliance documentation in App Store Connect under App Information → App Encryption Documentation. Apple’s guidance indicates that this type of review normally takes about 2 business days. It has now been more than three weeks. The document has remained in review since September 5, and no key value has been issued. I also contacted Apple Developer Support 3 times by email but I have not received an answer to my problem, or even a hint of a resolution. All I get is a canned reply blowing me off claiming "someone will get back to you." THEY NEVER DO. This 3 week "waiting for review" issue for the document is blocking me from submitting any and all app updates. I can't get an answer if it been assigned to a reviewer, or is it still waiting in a queue. I can't get an answer if the pending document is no longer applicable if I submit a new build that uses no proprietary encryption. I can't get ANY ANSWERS AT ALL. I would love to submit/update my app but EVERYTHING is on hold because Apple has had the export-compliance documentation "in review" since September 5th, 2026. Anyone else have this issue? How did you resolve it? Do you have any advice? Thanks in advance.

Hi all, I’m hoping someone from Apple or the community can help. Our app Lazy Watch (Bundle ID: app.lazywatch) was submitted for App Store distribution review and was rejected on Sunday, August 2. We reviewed the feedback from App Review, fixed the issue, and resubmitted the app the following day, August 3. It has now been 6 days since the resubmission with no update or movement. Details: • Original rejection: August 2 • Issue identified by App Review: Fixed • Resubmitted: August 3 • Current status: Waiting for Review • No further communication from App Review • Unable to reply to the original App Review message in App Store Connect • Updated submission was successfully submitted for review We understand that review times can vary, especially after a rejection, but we’re concerned because there has been no movement or communication since the resubmission. We also cannot reply to the previous review message through App Store Connect, so we’re unsure whether there is anything else expected from us or whether the new submission is simply still waiting in the review queue. Could someone from App Review or WWDR take a look, or point me to the appropriate escalation path? We’re happy to provide any additional information needed. Thanks in advance.

App: Mirra: You in Any Photo (App ID 6806898848), version 1.0. Latest Submission ID: 06677de2-a0fa-489c-8635-65998191f4e6. We have received the same Guideline 1.1 rejection three times, each with identical wording: "Specifically, the app includes templates for generating content showing people making intimate contact with each other, such as hugging, kissing, or other intimate templates." We are asking for help identifying what App Review is referring to, because the app does not contain templates of any kind: There is no template gallery, preset list, sample scene, or bundled content anywhere in the app. The asset catalog contains only the app icon and an accent color. The app has one function: the user supplies a reference photo (from their own library or a link they share) and the app renders that scene with the user's own enrolled face. Our server records show that no images were generated from the review account in any of the three review sessions. The service already declines any reference image showing more than one person, and the next build restricts generation to single-person photos end to end, with the reason shown on screen. Each resubmission included these facts in the review notes and returned the identical paragraph. We have replied in the Resolution Center and requested a call. If anyone from App Review can tell us the specific screen, screenshot, or asset that is being read as a template, we will remove it immediately. Otherwise we would be grateful for a review of the actual build. A demo account with pre-enrolled selfies is in App Review Information. Thank you.

Hi everyone, I wanted to check whether other developers are currently experiencing longer-than-usual App Review waiting times. We are submitting the first public release of our iOS app, LongTable. Timeline: September 25: App Review provided feedback under Guideline 1.2 regarding user-generated/anonymous content. We implemented the requested moderation, reporting, blocking and safety changes. September 28: We replied to App Review explaining the changes and resubmitted the updated build. The submission has remained in “Waiting for Review” since September 28 and has not yet moved to “In Review.” We contacted Apple Developer Support yesterday to check whether anything is preventing the submission from progressing. There are currently no outstanding messages or actions requested from us in App Store Connect. Is anyone else currently seeing similar waiting times for a first app or a resubmission after App Review feedback? I’m mainly trying to understand whether this is part of the current review queue or whether there is anything else we should check on our side. Thank you.

I’m very disappointed with my experience with Apple Developer and App Review. My app was supposed to be published between September 30 and October 1. For submission 4fe9a897-d64f-4757-b0d9-6e5ca0dab073, Apple contacted me on September 30 at 1:18 AM with the following request: “This app has been submitted by a developer account that has a limited App Review history. We need additional information to better understand the app and complete the review.” I provided all the requested information and replied at 1:41 AM on the same day, only 23 minutes later. Since then, I have received no approval, rejection, or request for additional information. My submission is simply stuck in review. This delay is directly affecting my project. I planned my launch around these dates, and I’m now losing the opportunity to monetize my app on iOS because I’m still waiting for Apple. What makes this even more frustrating is the difference in developer experience. I paid $25 for Google Play, and Google has been much faster and more supportive throughout the publishing process. With Apple, I’m paying $99 per year, but so far my experience has been slower and more difficult. I understand that App Review is important and that new developer accounts may require additional verification. However, after providing all the requested information immediately, I expected at least an update on the status of my submission. Could someone from Apple please help me understand what is happening with my review and whether anything else is required from me? I simply want to publish my project and start serving my iOS users.

I got a rejection and resubmitted my app and it was 7 days saying ”Waiting for review”, noting that it was 5 hours only for getting a rejection. i tried to reach out the support and opened a ticket with case ID 102981629206 and nothing happened since then!!

Can not update app privacy information about tracking user after remove the tracking functionality and "NSUserTrackingUsageDescription" from info.plist. Always reminds us App contains "NSUserTrackingUsageDescription"

I'm trying to submit my app version together with two auto-renewable subscriptions (both in the same subscription group), and one of the two subscriptions will not submit, while the other submits with no issue. Setup One subscription group ("Crucibull Pro") with two subscriptions: Annual — $49.99/year — submits fine Weekly — $1.99/week — fails to submit Both are being submitted together with a new app build in a single review submission. The errors I get (they vary, none are field-specific) "There are errors with one or more of your items. To fix them, you need to remove the items and add them again to your submission." "Sorry, something went wrong. Try your request again." "An unexpected error was encountered when submitting for review. If the issue persists please contact us." Critically, there is no red/field-level error anywhere on the Weekly subscription's page — its status is "Prepare for Submission" and every field is filled. What I've tried (nothing has worked) Verified every field on Weekly: reference name, product ID, 1-week duration, availability (all countries), price ($1.99 with a valid start date), localization (display name + description), tax category, and an App Review screenshot. Compared Weekly side-by-side with Annual (which submits fine) and matched every field. Changed Weekly's Tax Category to "Match to parent app" to match Annual. Removed and re-added the items to the submission (per the error message's advice) multiple times. Configured the subscription group ranking/levels. Deleted the original Weekly subscription and recreated it from scratch with a new Product ID — same result. Confirmed App Store Connect is stable (System Status all green) and still errors. Tried fresh submissions, different browser/incognito, and re-uploading the screenshot. Current state The Annual sub and the app build are ready and submit fine. The Weekly sub is fully configured, identical to Annual, freshly recreated, on a stable platform — and still throws generic submission errors with no indication of what's actually wrong. Question Has anyone seen an auto-renewable subscription that's fully configured (and identical to a working one in the same group) fail to submit with only generic errors and no field-level detail? Is there a known backend/propagation issue, or a hidden requirement I'm missing? Any way to see the actual validation failure? Thanks in advance.

What is going on with Apple App Review??? for a week they are not responding, didn't even start reviewing my app which means that I can't even get it tested with external developers. This is a shockingly bad service from a team that is usually reasonably quick. Does anyone else experience these horrible wait times???

I’m trying to understand what is happening with App Review right now because this has gone far beyond the normal review timeline. My first app submission received a Guideline 2.1 – Information Needed request on September 25. I replied the same day with everything requested, including: a physical-device screen recording detailed explanations of the app’s purpose and functionality information about the services provided and availability Since then: Sep 25: All requested information submitted Sep 28: Followed up again in the App Review message thread Sep 30: Opened an App Review Status support case Oct 2: Still no response from App Review and no substantive response from Developer Support The submission has now been sitting unresolved for 7 days after I provided all requested information. What makes this especially frustrating is that there is effectively no visibility into what is happening. There is no indication whether the response has been reviewed, whether the submission has been reassigned, whether additional verification is taking place, or whether it is simply waiting in a queue. I understand that reviews can occasionally take longer, but having both App Review and the App Review Status support channel remain completely silent for days makes it very difficult for developers to know whether the case is actually being processed. I’m also seeing multiple recent reports from other developers experiencing long delays after Guideline 2.1 requests, first submissions, and review follow-ups. Is anyone else currently experiencing the same issue? For those who recently went through this, how long did it take before App Review responded again? I would particularly appreciate clarification from Apple on whether there is currently a backlog affecting these types of submission.

Hey, we're stuck in a loop and need help from App Review. App: Latent: Focus Camera (Apple ID 6788947658) Submission: 302fb800-e336-4f51-afef-6bdffdc59320, version 1.0.1 (30) Latent is free. Build 30 has no in-app purchases, no paywall, and no purchase code. We keep getting rejected under 2.1(b) because the reviewer can't find "Latent Pro Yearly" (6813310670) and "Latent Pro Monthly" (6813311816) in the binary. That's correct, they aren't in it. They're leftovers from before we went free. The rejection says to remove them from App Store Connect. We can't: They were never approved. Both show Developer Rejected, with 0 territories, and they aren't part of the submission. There's no Delete button in App Store Connect. DELETE /v1/subscriptions/{id} returns 409 SUBSCRIPTION_DELETE_NOT_ALLOWED. The subscription group can't be deleted while those two are in it. We replied in Resolution Center on Sept 29 and resubmitted. Can someone remove these two subscriptions on your side, or let the reviewer know they aren't part of this version? Thanks, Malcolm

Hello App Review team, Our first app has been in "Waiting for Review" since 28 September 2026, and the delay is causing real financial loss to our business. App: Luxe Cuisines (iOS, version 1.0.0, build 37) Apple ID: 6786324195 Submission ID: 59403325-37eb-40ac-8056-b0384f2fa367 Support case: 102983424776 Timeline: 27 Sep 2026: submitted. The same day we received "Guideline 2.1 - Information Needed - New App Submission". 28 Sep 2026: we replied in App Store Connect with everything requested, including the screen recording, and resubmitted. Since then: "Waiting for Review", with no further message. Luxe Cuisines is a restaurant business in Abuja, Nigeria. We had hoped to launch our campaign on Nigeria's Independence Day, 1 October, and we missed it. Rented advertising materials and paid influencers are on hold, and the wait keeps adding costs we never planned for. Our Android version is already live on Google Play, so our iPhone customers are the only ones who cannot get the app, and we cannot announce the launch without them. We also could not send an expedited review request. The Contact App Review form shows "There are no apps associated with this team" for every team on my account, in two different browsers. Could someone from App Review please check whether this submission is progressing normally, tell us if anything more is needed from us, and expedite it if possible? Thank you.

Hi everyone, After a year of work I submitted my first app (a game) on September 21. It was in "Waiting for Review" until September 25 and has been "In Review" since then, so 11 days in total now. Is this normal at the moment? Everything I find online says most apps are reviewed within a day or two, so I'm wondering if I did something wrong or if this is just how it is right now. I did see a few other posts here with similar waiting times. It's my first submission and it also includes my first in-app purchases. Could that be why it takes longer? I contacted App Review through the contact form on September 30 but haven't heard anything yet. I haven't resubmitted anything, because I read that it puts you back at the end of the queue. One more question: will updates take just as long, or are they usually faster once the app is live? For context, the game has had 10+ testers for a few months, and Google Play approved the same version a couple of days ago. Thanks!

Hello, I’m looking for assistance with an App Store submission that appears to have stalled after a Guideline 2.1 – Information Needed request. App: Costante: Trading Discipline Version: 1.0.0 Build: 6 Timeline: September 25: App Review requested additional information under Guideline 2.1. September 25: I replied the same day with all requested information, including a physical-device screen recording and detailed answers regarding the app’s purpose, services, availability, and functionality. September 28: I followed up through the App Review message thread in App Store Connect. September 30: I contacted Apple Developer Support regarding the delay and received confirmation that a support case was opened. October 1: There has still been no further response or progress on the submission. Could someone from the App Review team please check whether this submission is still actively being processed, and whether any further action is required from my side? I can provide the Submission ID and Developer Support Case ID privately through the appropriate Apple support channel if required. Thank you.

Hello, Our first submission for HAVN911 has been in “Waiting for Review” since September 26, 2026, and has not yet entered the review process. We understand that review times can vary, but the app has now remained in the queue for five days. We have already: Submitted an expedited review request Contacted Developer Support Confirmed there are no outstanding messages or requests for information in App Store Connect Developer Support confirmed that the app is still in the review queue, but we have not been able to determine whether there is an issue preventing the review from starting. Could someone from the App Review team please verify that this submission is correctly queued and has not become stuck? We are ready to respond immediately if any additional information is required. Thank you.

Hello, I’m looking for assistance with an App Store submission that appears to have stalled after a Guideline 2.1 – Information Needed request. App: Costante: Trading Discipline Version: 1.0.0 Build: 6 Timeline: September 25: App Review requested additional information under Guideline 2.1. September 25: I replied the same day with all requested information, including a physical-device screen recording and detailed answers regarding the app’s purpose, services, availability, and functionality. September 28: I followed up through the App Review message thread in App Store Connect. September 30: I contacted Apple Developer Support regarding the delay and received confirmation that a support case was opened. October 1: There has still been no further response or progress on the submission. Could someone from the App Review team please check whether this submission is still actively being processed, and whether any further action is required from my side? I can provide the Submission ID and Developer Support Case ID privately through the appropriate Apple support channel if required. Thank you.

Hi Apple team, I’m developing Awaira, an iPhone app that runs real-time, on-device camera detection during a user-initiated support session. Its purpose is to help users notice hand-to-hair behavior. The user explicitly starts and stops the session; the camera indicator remains visible; camera frames are processed on-device; and the app does not record or transmit video. A common user request is to continue the session while using another app. On Android, this can be implemented with visible foreground-service behavior. On iOS, the capture session stops when Awaira is no longer foreground. I found AVCaptureSession.isMultitaskingCameraAccessSupported and isMultitaskingCameraAccessEnabled. The documentation says iOS 18 apps using UIBackgroundModes = voip may support multitasking camera access, and Apple’s PiP documentation discusses video-call apps. We do not provide a genuine person-to-person VoIP or video-calling service, and we do not want to misuse the VoIP background mode or create a fake call solely to keep camera detection active. Could Apple clarify: Is there any App-Review-approved API or entitlement for this kind of explicit, visible, user-initiated on-device camera session to continue while another app is foreground? Is declaring voip and using the multitasking-camera API permitted only for genuine VoIP/video-call apps? If no current approved path exists, is there a recommended design pattern for this accessibility/health-oriented use case? We will only ship an implementation that complies with the intended purpose of Apple’s APIs and App Review Guidelines. https://developer.apple.com/documentation/avfoundation/avcapturesession/ismultitaskingcameraaccesssupported Thank you.

Desde 16 de setembro de 2026, o TestFlight parou de funcionar para o nosso aplicativo e nada do que fazemos resolve o problema. Parece ser o mesmo problema com o contrato beta descrito nos tópicos 814565 e 821498. Aplicativo apploja001: ID Apple 6769057506, ID do pacote com.grupolb.apploja Versão 1.4.3, O que aconteceu Em 16 de setembro de 2026, todos nossos apps expiraram no mesmo segundo. Ninguém da nossa equipe as expirou. As versões 1.4.2 e 1.4.1 ainda estavam validas e foram expiradas. Desde então, nenhum testador consegue instalar nenhuma versão, interna ou externa. As versões 1.4.9 e 1.4.7 são processadas como válidas e estão disponíveis para nosso grupo interno, mas ao clicar em Instalar no TestFlight, aparece a mensagem: "Não foi possível instalar o apploja. O aplicativo solicitado não está disponível ou não existe." Todos os contratos relacionados à área comercial estão ativos, não há pendências e a associação está ativa. As informações do teste (descrição, e-mail para feedback, contato para revisão) e o contrato de licença beta foram preenchidos. A conformidade com as normas de exportação está definida (criptografia não isenta não está ativada). As novas compilações falham da mesma maneira. Apagar o aplicativo do dispositivo antes de instalar resulta no mesmo erro. O sistema de verificação de disponibilidade da Apple não indica nenhuma interrupção. Tenho o caso Nº do caso: 102965543896 aberto desde 16 de setembro de 2026 sem retorno. Alguém da equipe de suporte poderia verificar meu caso;